Crawler time issue

Dear Experts,
I have an issue regarding the custom crawler which I had created for the web repository.
System Landscape - EP 2004s SP 14.
I have created a custom crawler (System Admin -> System Config -> Knowledge Management -> Global Services -> Crawler Parameters) by duplicating a standard crawler.
This custom crawler has following parameters -
No. of retrieving threads = 4.
No. of providing threads = 4.
Follow Redirects = ON.
Now when I try to re index  the web repository it takes so long (About 20 - 25 hours)  to deliver about 300000 documents.
Even for the incremental index it takes 19 hours to deliver about 100 documents.
I don't think this is a normal behavior of the crawler.
Everything looks fine except this is taking lot of time to deliver the documents .
Note - 1. I don't find anything in the default trace regarding crawler.
          2. The web repository is a 'static' web repository with start page information.
          3. As per customer there is no change on the web server.
Any advice how to speed up the crawler.
Thanks & Regards,
Amit

Hello Amit,
You can speed up the queue parameters refer to this thread.
<a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=526552&messageID=3973244#3973244">https://www.sdn.sap.com/irj/sdn/thread?threadID=526552&messageID=3973244#3973244</a>

Similar Messages

  • Time issue- urgnt

    HI Expert !
    I m using this code .
    LTIME TYPE SY-UZEIT
    T1 TYPE SY-UZEIT VALUE 030000,
    T2 TYPE SY-UZEIT VALUE 050000,
    BUT WHEN I M USING T1 AND T2  in loop ( if  statement ),ITS value r
    T1 =  082000.
    t2  = 131100 .
    if  t1(6)  t2(6 )
    ltime (6 ).
    then ok . but in this i wont be able to make comparison in if statement
    how i can resolve this time issue
    i dont want to include timings between 3.00 a.m and 5.00 ,
    for this i have used this code but its not updating data for any employee , is this code correct or not.
    OPEN DATASET PA_FILE FOR INPUT IN TEXT MODE ENCODING DEFAULT.
    DO.
    READ DATASET PA_FILE INTO REC.
    CLEAR WA_PUNCHES.
    IF SY-SUBRC <> 0.
    EXIT.
    ENDIF.
    WRITE: / REC.
    if NOT ( WA_SCORE-LTIME GE T1 AND WA_SCORE-LTIME LE T2 ) .
    AND
    ***( WA_SCORE-TERID NE TR3 AND
    ***WA_SCORE-TERID NE TR4 AND
    ***WA_SCORE-TERID NE TR5 AND
    ***WA_SCORE-TERID NE TR6 AND
    ***WA_SCORE-TERID NE TR7 AND
    ***WA_SCORE-TERID NE TR8 ) .
    WA_SCORE-PERNR = REC+0(8) .
    WA_SCORE-LDATE = REC+9(8) .
    WA_SCORE-LTIME = REC+18(6) .
    WA_SCORE-CANID = REC+25(8) .
    WA_SCORE-TERID = REC+34(4) .
    APPEND WA_SCORE TO IT_SCORE.
    ELSE .
    EXIT .
    ADD 1 TO COUNT.
    ENDIF .
    ENDDO.
    plz help me . its very imp. program .
    thanks

    Hi,
    Pass values in quotes
    T1 TYPE SY-UZEIT VALUE '030000',
    T2 TYPE SY-UZEIT VALUE '050000',
    Can you please check once again after making this change in debug mode, values of T1, T2 and LTIME.
    ashish

  • Time issue seems odd to me

    I put a secondary domain and po at a remote location - running 8.03 on Sles/Oes and moved all of the "local" users to that po.
    while everything seems to run ok we have a weird time issue.
    Mail into and out of the new mailboxes shows a three and a half hour time difference both in the date column in the groupwise client and in the printed header of the email.
    The odd thing is that if I go to the properties of the email - the Creation date and the File date and time are both correct.
    I can't see any time issues with the servers (primary or secondary) and especially something that would be 3:30 minutes off
    there is a timezone difference between the pri and sec but that's just 1 hour.
    Any thoughts?
    As a workaround I have had my users add the creation column to see when they actually received the email as our clients have time critical projects.
    Thanks
    Dennis

    Danita,
    Thanks for the reply - Oh how I wish it were that easy - I've checked and double checked the PO object and the domain object - both say US eastern time.
    If I send email from a mailbox on the secondary to the primary - everything is correct (a 1 hour time difference - Eastern to Central)
    If I send mail from a mailbox on the primary to the secondary - it shows up right away, but says 3:30 minutes later than it should (in Date/Time, but not in Created)
    If I send email from a mailbox on the secondary to a GMail account - the header shows the 3:30 offset, but the properties of the mail shows correctly.
    I would be happy to send email from that po to anyone that wants to see for themselves.
    Other than the PO Object and the DOM object - Where should I be looking for a time difference
    and how would it be getting UTC minus 30 minutes - - Is there a special timezone out there for Hy Brasil?
    The workstations all get their time settings from "time.windows.com" the windows default.
    Thanks for looking into this - I just hope that I can get it figured out because as small of an issue that I think it is (they get their email, it just looks like it gets read before they officially receive it)
    but it seems that this office uses the received time to track how long it takes them to do their work.
    Dennis

  • Real time issue

    Hi all,
    Can any body plz send me some FICO real time issue on [email protected]
    and plz tell me hw shld I prepare for interview
    Thanks & Regards
    Vaibhav

    Hi Balraj,
    In the normal practice, developers will try to find the similer infocube (as per the requirement) in the Business content. But always you will not be lucky to find such infocube in Business content. You need to create at your own to suite the business requirements. Regarding the characteristcs & key figure, it 's again depend on the requirements. Calculated object can be assign as key figure like. Sales qty, revenue & net sales etc. where as Dimesion (characteritcs) will be purely depends on the reporting point of view. Like Customer, Material & Sales Document type etc.
    Hope this will help you !
    Thanks,
    Sanjiv

  • Execution Time Issue

    Help Please!!!
    I've been searching for an execution time issue in our application for a while now. Here is some background on the application:
    Collects analog data from a cDAQ chassis with a 9205 at 5kHz
    Data is collected in 100ms chunks
    Some of the data is saved directly to a TDMS file while the rest is averaged for a single data point. That single data point is saved to disk in a text file every 200ms.
    Problem: During operation, the VI that writes the data to the text file will periodically take many hundreds of milliseconds to execute. Normal operation execution times are on the order of 1ms or less. This issue will happen randomly during operation. It's usually many seconds between times that this occurs and it doesn't seem to have any pattern to when the event happens.
    Attached is a screenshot of the VI in question. The timing check labeled "A" is the one that will show the troubling execution time. All the other timing checks show 0ms every time this issue occurs. I simply can't see what else is holding this thing up. The only unchecked subVI is the "append error call chain" call. I've gone through the heirarchy of that VI and ensured that everything is set for reentrant execution. I will check that too soon, but I really don't expect to find anything.
    Where else can I look for where the time went? It doesn't seem to make sense.
    Thanks for reading!
    Tim
    Attachments:
    Screen Shot 2013-09-06 at 9.32.46 AM.png ‏87 KB

    You should probably increase how much data you write with a single Write to Text File.  Move the Write to Text File out of the FOR loop.  Just have the data to be written autoindex to create an array of strings.  The Write to Text File will accept the array of strings directly, writing a single line for each element in the arry.
    Another idea I am having is to use another loop (yes another queue as well) for the writing of the file.  But you put the Dequeue Element inside of another WHILE loop.  On the first iteration of this inside loop, set the timeout to something normal or -1 for wait forever.  Any further iteration should have a timeout of 0.  You do this with a shift register.  Autoindex the read strings out of the loop.  This array goes straight into the Write to Text File.  This way you can quickly catch up when your file write takes a long time.
    NOTE:  This is just a very quick example I put together. It is far from a complete idea, but it shows the general idea I was having with reading the queue.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    Write all data on queue.png ‏16 KB

  • Time issues? time zone settings appear in two places

    If you leave the default "set time and date automatically", you see the time zone support below and you can check it or uncheck. You can then set your time zone there. But if you uncheck the automatic date and time, you get another time zone choice and the default is Cupertino, of course. I wonder if that's the problem with some of these time issues.
    I've since unchecked automatic date and time, set my city's time zone, then rechecked automatic. The only weirdness I've seen was with an excel spreadsheet where the time was correctly shown on my mac, but not on the iphone. Unfortunately I don't have that sheet anymore or I'd try again to see if it works now.
    Just a thought.

    I noticed the same thing and did the same thing you did because my time was off by several hours each time I turned the phone on...after it being off overnight. When it was off by only 1 hour I could turn the Auto OFF then 'tap' the timezone (already set to the correct city) and the time would instantly correct itself. Then I'd turn Auto back ON.
    Turns out that my time issue was related to having the SIM PIN enabled. Once I disabled that, the time's been correct every day.

  • Real  time issues

    hi there,
    can any one share some of the issues that have been dealt with in real time. i.e.during blue print stage, <b>especially in realisation stage</b>, final preparation stage
    puhlease answer this question immediately

    Hi Medasani,
    Real time issue you can get it from the Sap support consultants. Hence, getting all the information is very difficult.
    In what basis you are asking let me your requirements.
    For Example :- Tolerance limits is has to increase to Rs.1 to Rs.100. for employees and vendor / customer. This is the issue from client.
    How you will decide that to increase.
    First you should understand the clinet work flow and get the approval from client end (core Team) then you have to increase meanwhile you have to decide the % also.
    Oba3 /Oba2
    Warm Regards,
    Sivakumar Sathiyamoorthy

  • [SOLVED] Yet another time issue...

    Hi there,
    I'm having some crazy, hair pulling, head banging UTC time issues on both my dual boot (Arch & Windows 8) desktop and single boot laptop.
    I've been searching and following a mulitude of old threads and the official Wiki guide, however, I simply cannot get UTC time to stay correct between reboots. I've installed Arch a fair few times now, both before and after the switch to systemd and in dual and single boot setups and have never had time related issues like this before...
    Here's a run down of the whole sorry story....
    Fresh install - set time with hwclock --systohw utc as suggested in the beginners guide.
    First boot - time an hour out - huh? cat /etc/adjtime and ls -l /etc/localtime - everything as it should be... UTC and symlink to /usr/share/zoneinfo/Europe/London. Nonetheless I duly follow the Time guide on the wiki, get to know timedatectl a bit, and soon after, time is set to be correct. Great.
    Reboot. Time an hour out. Whaaaa??. Start googling, finding a plethora of bbs links to others with similar issues, decide to use NTP. Install, ntpd -qg. All good again. Time right. Phew...
    Reboot. Nope. Arrrrgggghhhh. (Bare in mind - at this point I haven't even booted the Windows 8 disc, and I went through the exact same process on my Arch only laptop...)
    More googling, thread reading. Find out that hwclock and ntp might be in conflict. Delete /etc/adjtime, reinstall tzdata, re-follow Time article to the letter and reenable NTP to start at boot.
    Reboot - time is foward an hour yet again. Bang head repeatedly on desk. Then suddenly - 10 mins or so after boot - NTP kicks in, and time is magically goes back an hour to the correct time! Surely NTP should be doing this early in the boot process, not 10 minutes after? But OK, at least something is happening...
    Next I dare to boot into Windows, and yup, time an hour out. Expected, but frustrating nonetheless. Add the registry tweak as suggested in the guide, and turn off the Windows time synchronisation. During which I noticed that Windows 8 time is set to UTC by default, not localtime, which is what the wiki says. Is this a Windows 8 thing?
    I can't help thinking, that if this is the case, and the Wiki advise is written under the assumption that Windows time is always localtime, that perhaps this is the route of my problem....
    Anyway, Windows time all good now, reboot Arch, time again wrong untill NTP finally kicks in - sigh. Reboot to Windows. Time an hour back. Gaaaahhhh - WTF?!! reset it to be correct. Try again. Same thing. Oops, forgot to mention that on each reboot, I check the BIOS clock, which remains persistently correct during the whole debarkle...
    Ok, so I try without the registry hack and turn Windows sync back on. Still fucked. I try various combinations of the two, I try resetting Arch time over and over again. With NTP - late sync. With hwclock only, or both hwclock & NTP - totally fucked! Eventually, I give up on UTC in Arch, set it localtime, delete registry key, turn Windows time sync back on, and thus far all good......
    TL;DR - couldn't get hwclock to set UTC time correctly across reboots. NTP worked (sort of), but after each reboot it would take ten minutes for the time to sync and the clock to move back an hour to the correct time. Localtime just works...
    My question is - why is the wiki (and the timedatectl status output for that matter) - so adamant that we should use UTC? From what I can gather, as long as I boot Windows around the DST time. or manually move the clock forward or back an hour - all should be well, no? Or are there other issues that I may run into that I've missed? The thing I'm most concerned about is data corruption due to timestamp issues...
    Also, why does the wiki repeatedly say that Windows uses localtime, when this doesn't appear to be the case in Eight? Does the wiki need updating or is Windows lying to me? I know which I'd put my money on ;-)
    Finally can anyone explain why my time was always an hour forward after a reboot, even when the time was set correctly before, the BIOS showed the correct time, and NTP was in use?
    Sorry for the crazy long posting, but this issue has been driving me totally batty!! Any light-shedding greatfully appreciated :-)
    Last edited by knowayhack (2013-08-10 15:24:09)

    Ok, so I set the clock back an hour in the BIOS, booted Windows - time right - YAY.
    Rebooted Arch - time right. OMFG - pure joy!!!
    I have to say, I still find it odd that this is how it works, and would like to confirm that things are looking as they should in the output from the following commands....
    toby@archy ~ > timedatectl status
          Local time: Sat 2013-08-10 15:42:56 BST
      Universal time: Sat 2013-08-10 14:42:56 UTC
            Timezone: Europe/London (BST, +0100)
         NTP enabled: n/a
    NTP synchronized: no
    RTC in local TZ: no
          DST active: yes
    Last DST change: DST began at
                      Sun 2013-03-31 00:59:59 GMT
                      Sun 2013-03-31 02:00:00 BST
    Next DST change: DST ends (the clock jumps one hour backwards) at
                      Sun 2013-10-27 01:59:59 BST
                      Sun 2013-10-27 01:00:00 GMT
    toby@archy ~ > sudo hwclock --debug
    sudo: timestamp too far in the future: Aug 10 16:39:24 2013
    We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:
        #1) Respect the privacy of others.
        #2) Think before you type.
        #3) With great power comes great responsibility.
    [sudo] password for toby:
    hwclock from util-linux 2.23.2
    Using /dev interface to clock.
    Last drift adjustment done at 1376148264 seconds after 1969
    Last calibration done at 1376148264 seconds after 1969
    Hardware clock is on UTC time
    Assuming hardware clock is kept in UTC time.
    Waiting for clock tick...
    ...got clock tick
    Time read from Hardware Clock: 2013/08/10 14:43:20
    Hw clock time : 2013/08/10 14:43:20 = 1376145800 seconds since 1969
    Sat 10 Aug 2013 15:43:20 BST  -0.953640 seconds
    Is it OK to now reinstall NTP to keep the clock in sync on Arch, and are the Windows reg tweaks still necessary on Windows 8?
    Thank you guys SOOO much for all the unbelievabley speedy help on this issue - you have no idea how much this has been stressing me out!!
    Last edited by knowayhack (2013-08-10 14:54:31)

  • Communication channel availablity time issue

    Hi All,
    We want to schdule communication channel every  mid night ,but when i tried to give the time there is a diffrence of about 6 hours .so evry time if in need to schdule need to calculate and schdule the time ,checked out the server timing it is similar to system time ,even messages in MONI also showing the correct time ,do we need to check anything in the adpter engine to correct this time diffrence.
    Appreciate reply on this.
    Thanks,
    Madhu

    Madhu
    Iu2019m not sure if this is exactly your issue, but please see the following links concerning time issue in XI.
    Time setting is differnt in sxmb_moni and RWB
    Different time stamp in sxmb_moni and RWB
    Hope this helps.
    PJ

  • SEM-BPS Real times issues

    Hi Gurus,
    I'm new to SEM-BPS Real times issues also some interview questions on SEM BPS. How we want to answer please forward to my email id: [email protected]
    thank regards
    Suresh

    Have you tried posting to th eBusiness Planning forum which is focused on SEM/BPS?  It's under the Business Intelligence category.

  • Please tell me some real time issues faced by u in SCRIPTS

    please tell me some real time issues faced by u in ur experience

    First understand SAP scripts are client dependent..changes automatically not reflects in all development client once it is change in once client.
    We mostly see alignment issue in SAP script it is mostly because of printer settings etc...
    Also we may have few problems when printing unicode characters.. for printing double digits characters... like Japanese, chinese, korean etc.. we should have a printer with unicode enabled..
    Regards,
    SaiRam

  • Real time issues faced during Sap Implementation.

    Hi All,
    Please let me know some real time issues faced during SAP end to end implementation. Hw did u get over the issues.
    Issues faced during Production Support.
    I have an F2F interview. Please help me out.
    Regards,
    Somya

    Hi,
       This is Srinivas If u dont mine can u help me in Sending me the solutions to me what type of issues we will face in sap/bw implementation like issues and defeacts  can u send to my mail  [email protected]  can u give me solution for error9,error8,return8 can able to plz help me .
    Regards,
    Vasu.

  • RV220W System Time Issue in Combination with WiFi Active Time

    Hi
    Have system time issues with rv220w!
    Setup:
    Note that the real time is 17.32 (bottom right) but the system time is 16.20, result 1h offset (sad that the possibility to configure summertime start/end is missing)
    Setting up the WiFi active time from 5.30PM until 6PM (testing only):
    Note that the real time is 17.44, the WiFi is "Disabled". The RV220W system time is 16.44 with setting "CET +1h".
    BUT:
    Even when i change the RV220W system time to a Time/Date offset GMT +2h EET has this no issue to the WiFi time profile i set up. The WiFi stay down.
    Note:
    The WiFi Active Time Settings only working correct when the Clock Source is setting up with "Set Date and Time Manually" (in "Administration" "Time Settings"), but that is not the way.... i don't like to configure time settings manually (no system administrator will do that tinking)
    Conclusion:
    I think that the WiFi Time setting does not work fine, mean that the WiFi does not include the configured offset as usually system does....
    Further:
    RV220W firmware is up to date....
    Hope Cisco will fix that and add the summer time feature (like in other systems and other manufacturer) in the next FW.....

    GJinAmsterdam wrote:
    I have a MacBook upgraded from Tiger 10.4 to *Snow Leopard OS X 10.6.1.* I'm now using *Time Machine* to make back-ups on a *MiniMax external drive* through an USB connection. However, I wish to make wireless back-ups by connecting the external drive to my *Airport Extreme*. I learned that this wasn't possible until the recent release by Apple of the software update "*About Time Machine and AirPort Updates v1.0*".
    this has been possible for a long time, since about February 2008 when those updates came out.
    The minimum system requirement for this software update is OS X 10.5.2. I should think this requirement is met because I have upgraded to 10.6.1. But when I try to install the software I get the message that the system requirement is at least 10.5.2. and as a result *I can't continue installing*. Apparently my OS update is not recognized by the software. Is there a solution for this problem? Many thanks.
    you don't need to install those updates. they are for leopard, not snow leopard. you should be fine as is. do keep in mind that TM backups to air disks are not "officially" supported but they have worked for a long time. also, keep in midn that you'll need to start a new backup sequence once you move the drive to AEBS as remote backups are stored differently from directly attached ones.

  • Real time issues in fdm

    What are the real time issues in fdm

    Nice and vague, try to be more specific with your questions and you will likely receive a better response.

  • OVM 3.0.3 Time Issues

    I have a two server pool and after the reboot from installing the 3.0.3-150 patch, the two virtual servers in my pool came back online with drastically different RTC times. Their ntpdate offsets at boot were 23,375 seconds and 21,577 seconds; before this reboot, the largest ntpdate offset had been under 0.002 seconds. Due to NTP, the systems' time on the virtual servers were corrected; however, the RTC remained wrong. This was confirmed by using hwclock after soft linking /dev/rtc to /dev/rtc0.
    All my 32bit PVM guests are running kernel 2.6.18-238.1.1.0.1.el5xen and I've been able to fix this issue by configuring xen.independent_wallclock = 1. However, my 64bit PVM guests are running kernel 2.6.32-200.13.1.el6uek and can't be configured with xen.independent_wallclock. The 64bit guests don't get hung when migrating between the servers; however, the time on the 64bit PVM guests still jumps by 30 minutes when I migrate between the servers. NTPD on the guest doesn't update the clock because the offset exceeds the sanity limit of 1000 seconds. I can manually fix the system time by running ntpdate; however this would be something I'd need to check after each migration, which isn't practical. I've ran "hwclock --utc -w" on the virtual servers but they're already about 20 seconds fast after less than a week.
    Correct me if I'm wrong, but it's my understanding that the configuration of NTP on the virtual servers is only keeping their system times in check. If NTP isn't keeping the RTC of the virtual servers on time, then how can I ensure that my 64bit PVM guests are getting accurate time from the virtual servers when they live migrate? Or is there a way to make PVM's running kernel 2.6.32 keep time totally independent from the virtual servers?
    I didn't have any time issues on guest servers prior to 3.0.3 (this includes running OVM 2.2, 3.0.1, and 3.0.2). Because I never had issues, I never looked closely to how the virtual servers were configured. Did something get changed in version 3.0.3 that would cause these time issues?

    user4400470 wrote:
    I have a two server pool and after the reboot from installing the 3.0.3-150 patch, the two virtual servers in my pool came back online with drastically different RTC timesWe currently have a fix in QA to fix the symlink (which you've already done, it seems), which will allow the hwclock to be set correctly on boot/reboot.

Maybe you are looking for