Running regulatory tasks 1C 8.3. Background tasks: Features, Features, Setup

" In it, we will look at new features that do not concern the system interface, but significantly expand the provided functionality of the "1C: Enterprise 8" platform.

Applicability

The article discusses the "1C: Enterprise" platform version 8.3.4.437. All the functionality described in the article is updated to the editorial office 8.3.11.

Other innovations in "1C: Enterprise 8.3"

We will continue to get acquainted with the innovations of the 1C: Enterprise 8.3 platform.

Background and regulatory tasks in the File Information Base

In many typical platform configurations 8.2 There was a constant in which the user was specified under which tasks were performed in the file.

When the system is started, under this user, the expectation handler has occurred, which for a certain periodicity caused the embedded language method. PerformingPackets ().

Such an approach created additional difficulties and inconvenience to use regulatory tasks in the file database.

It could be especially critical when working with such configurations as "Complex Automation" or "Managing Production Enterprise"In which the regulatory tasks play a rather important role.

If it is FileIb then
=
Constants. Usually Full-planeThe WoversVariant. Focus();
If a gLNAGEVENED("Glotting user") =
Customer clipThen
// In the interval of seconds call the procedure for working with regulatory tasks
SupportedLentyLentyFyle FileVession();
IntervalTrack=
Constants. IntervaltlasprosarlamentAdnayaTaniyvifylevarisa. Pour();
If a IntervalTrack\u003d Uncertain
OR IntervalTrack\u003d 0 then
IntervalTrack= 60 ;
Ended;
Connectographicing("SupportedLameDadantedLameFilevation",
IntervalTrack);
Ended;
Ended;

In the platform 8.3 The work of background and regulatory tasks in the file information database is implemented without using the global context method PerformingPackets ().

Background and regulatory tasks are performed directly in one of the client applications (thin, thick client) or the web server extension.

The background task run by any session is performed by the same client application that initiated it.

Background tasks are performed sequentially, i.e. On one client application at one point in time, only one background task may be performed (including regulatory).

Regulatory tasks are performed only by one client application. To manage the start of regulatory tasks, the command line key is intended. AllowExecuteScheduledjobs..

Regulatory tasks are performed first in order to start the client application that does not prohibit the execution of regulatory tasks (for the prohibition of the session must be launched with the command line parameter AllowExecuteScheduLeDjobs -off.).

When this session is completed, execution proceeds to any of the remaining sessions running.

If the client application string explicitly specifies the need to start regulatory tasks (in the command prompt specified AllowExecuteScheduledJobs -Force), Regulatory tasks begin to be performed on it, regardless of the availability of other sessions.

Processing regulatory tasks occurs once every 60 seconds.

Note that the regulatory tasks of the application solution (in the file variant) started to be executed no earlier than 1 minute after the client application is launched. Starting with the edition 8.3.8, this time was doubled, and therefore the regulatory tasks begin to be made to the maximum 2 minutes after the client launch (in the file).

This solution is due to a decrease in the delay when the application starts. In addition, in release 8.3.7, the ability to quickly determine that the current session is a background task session. This is implemented at the expense of the new method of global context to get theseansinformational base (), as well as a new method at the information base session. OPENDFONEVENATION ().

The following is the code that illustrates the above described:

To enlarge, click on the image.

Calculation of checksums

In the platform, mechanisms appeared to calculate the control sums.

Recall that the checksum (hash) is a certain value calculated by the data set by using a specific algorithm and used to verify the integrity of the data when they are transmitted or stored.

Hischai can be used to check the identity of the data (for example, it is necessary to make sure that it is not damaged when transferring the file; check if there were changes to the file, and if so, then load it to the database again).

To do this, an object was implemented in the platform ChechirovatedAvailable on the server in a thick client, external connections, as well as on a mobile application server.

This object has two methods: Add () and To add a file()who update the hash sum with the data transmitted in the parameters.

Platform 8.3.4.437 Supports the calculation of the following hash functions: CRC32., MD5, Sha1, SHA256.. But functions Sha1and SHA256.not supported on a mobile platform.

Consider a simple example. It is assumed that on the server in the program directory there is a file " ragent.exe.". It is necessary to calculate MD5-Summage for this file.

To do this, create external processing, on the form of which will be placed Calculate. The handler contains the following code:

& Svalette
Calculate procedure (command)
Result \u003d. Calculate server();
Report (string (result));
Extrudresses
&On server
Function Calculate server()
Hash \u003d new Chechirovated(.Md5 hashfunction);
Hash.Daddlindile(Catalog Program() + "Ragent.exe");
Return Heshe.Hesumum;
Endfunction

In the editorial platform 8.3.10+ in the method Add () Object Chechirovated It became possible to use the stream of binary data, which significantly simplified their use in solving various application tasks to update hash-sums.

Work with secure versions of protocols SMTP / POP3.

In the platform 8.3 There is an opportunity to use protected versions of protocols. SMTP / POP3. (Terms are found SMTPS / POP3S. or Sslsmtp / sslpop3.).

For object InternetPootpofil New properties implemented:

• Usesslsmtp;
• Usesslpop3.;
• UnderstandingAutentificationSmtp;
• UnderstandingAutentificationPop3.

Properties AuthenticationSmtp.and AuthenticationPop3.object InternetPootpofilas well as enumerations PODSMTPAutentificationand POPOP3Anauthentificationuse it is not recommended - they are supported for compatibility.

Using a secure protocol SMTPS.makes it possible to send mail from 1C.using the mailbox Google.

Consider an example. On the form, we have a field for entering the subject of the letter and the address of the recipient, and to enter the text of the letter - the field of the formatted document.

To enlarge, click on the image.

Pressing the button Sendthe following code will be executed:

& Svalette
Procedure Send (command) mail \u003d new online pub; Profile \u003d new InternetPootpofil;
Profile. PressReserSmtp.\u003d "Smtp.googlemail.com";
Profile. Usersmtp.= “[Email Protected]” ;
Profile. Pallsmtp\u003d "PASSWORD";
Profile. Usesslsmtp\u003d Truth;
Profile. Portsmtp \u003d 465; Attempt
Mail. Conference(Profile);
An exception
Report (Description ());
Refund;
Celebrations; Postal informantExter= “” ;
Attachments \u003d new structure;
Text.ChelchHTML(Postal informantExter, Investments ); Postalization\u003d New Internet puberty;
Postalization. Practitioners. Add(To whom);
Postalization\u003d Topic;
Postalization. Whites. Add(Postal informantExter,
TytextapochetovoP.html.); Mail. Address ( Postalization); Mail. Follow();
Extrudresses

Note that in our example if the SMTP server could not send an email to the addressee (-m), then the method Mail. Send (Postal Communication) generated an exception. This caused certain inconvenience from developers, because The reason for the generation of exception was not obvious.

In the editorial board 8.3.9, this behavior has changed, and now the send method () returns compliance, the key of which is the destination, and the value is diagnostics from the mail server. This allows you to accurately determine the reasons for the unsuccessful email sending to each of the addressees. In compatibility mode with version 8.3.8, the behavior has not changed.

Two-sided printing

In the platform 8.2 The platform itself did not manage the double-sided seal, it was possible to manage this feature only using the printer driver.

In the platform 8.3 The ability to control bilateral printing for a table document, a graphic scheme (from the built-in language and interactively) and a text document (only interactively).

In the embedded language, system listings appeared:

• Typid softener(No, DVORSOPE, DORAVED);
• (Auto, Mirror Power, Mirror Slab, Understand).

And in objects Timberand Graphicshemproperties appeared Two-sided printingand Alternating distributionStranitsaWith which you can change the location of the printed pages.

In the editorial office of the platform 8.3.9, a new meaning was added to the system listing of tidylon Use the nastyprinter. Selecting this value allowed to use the printer settings when printing system documents. In compatibility mode with version 8.3.8, the behavior has not changed and the corresponding printer settings are ignored.

The information base publication dialog on the web server is more functional. Now publishing the configurator allows you to set all file settings. default.VRD..

To dialogue publishing a web client and Web services through the configurator is implemented:

• the ability to manage the availability of Web services by default (attribute pointenablecommon. Element wS.);
• the ability to control the execution of background tasks in the file (attribute allowExecuteScheduledjobs. Element wS.).

If flag "Publish Web Services by default" On the tab "Basic" Installed, when updating publishing, selected Web services will be published automatically.

Otherwise, Web services will be marked as nonposable. This flag matches the attribute pointenablecommon.element wS.in file default.VRD.Designed to configure the web client and Web services.

Attribute pointenablecommon.the WS element is responsible for the possibility of using Web services in this information base, which are published without explicit use of the use permissions (attribute enableelement point).

If the attribute is important true., then all Web services for which the attribute value is clearly not specified. enableelement pointwill be allowed to use.

Otherwise, the use of such Web services will be prohibited.

Setting "Background tasks in file mode" corresponds to the attribute allowExecuteScheduledjobs.wS element in file default.VRD..

Attribute allowExecuteScheduledjobs.manages the ability to execute regulatory tasks to the web server expansion for the information base file.

The attribute can take the following values:

• off- In this case, the web server extension will not perform regulatory tasks. Performing regulatory tasks will be the client application (if any), which connects directly to the information database, without using a web server.
• force- In this case, the web server extension will perform regulatory tasks.
  If the value of this attribute is not specified, the regulatory tasks will perform the application with which the first connection to the information base will be performed.

The publication window on the web service in the current release of the platform has become even more convenient and ergonomic. Now the parameters describing the OpenID authentication are made on a separate tab.

Numbering of information base objects

In the platform 8.3 recycled mechanism for automatic numbering of information base objects. Monitoring the uniqueness of the number or code (including the number or code obtained as a result of automatic generation) is always done during the entry of the object.

The text of the uniqueness of the uniqueness of the number or code is added to the indication of which number or code is not unique.

The use of the liberated number or code has changed. The new number or code is assigned without using the released numbers or codes, if there are already issued numbers or codes with a large (in order) prefix of the number or code.

Aggregate Language Language Language Data Layout System

In the language of expressions of the data layout system, new aggregate functions are implemented:

• Everyone();
• Any();
• Standard alternate degeneration ();
• StandardLonions Creatures ();
• Dispersion exhibition ();
• Dispersion sensor ();
• Covariance receptacle ();
• CovariarationSebors ();
• Correlation();
• REGRESSIONALLON ();
• Regressing ();
• Regressionicism ();
• RegressionR2 ();
• Regressing formed ();
• Regressing average ();
• Regressing averagesXX ();
• Regressing average ();
• Regressing averagesXY ().

As can be seen from the names, these are statistical functions, it means that the developers have the opportunity to create complex reports without resorting to the development of procedures for calculating statistical data.

To enlarge, click on the image.

As can be seen in the figure, there are no new features in the drop-down list, but if you manually enter them, the error message will not be, and the report will be formed:

Also represents the interest of a new feature ClassificationABC (). The result of the function of the function will be the class number, starting from 1 (1 corresponds to the class A, 2 - class B, 3 - class C, etc.).

We will demonstrate the work of this function. Create a new external report "Classification of goods" Based on the request:

CHOOSE
Costdranovanovari.Thovar,
Costbarovanovari.Colism
OF
Document. Source. TastersAS Costbatovaratovari

Determine the new calculated field Class:

To enlarge, click on the image.

We will configure resources as follows:

To enlarge, click on the image.

In user mode, the report looks like this:

In conclusion, we note that from the editorial board in the 1C 8.3 platform 8.3, the SCD mechanism is constantly improved and refined, and within our "newcomer" article data changes are not possible. Yes, it seems unnecessary, because, working on the current version of the platform, you can always use various reference systems to help with the analysis of a particular aspect of the work of this mechanism.

In addition, do not forget about our separate course, the professional development of reports in 1C 8.3 on the data layout system, which takes over all the subtleties and pitches to the atom when working with this mechanism. Look at the demo yourself and.

So, let's summarize the results. Up to this point, we also got acquainted with the new features of the "taxi" interface and managed forms, as well as with some previously provided capabilities of the platform itself. Now it's time to see which convenient features have become available and developer in the configurator.

How to speed up the work in 1C: Accounting 8.3 (edition 3.0) or turn off the regulatory and background tasks

2019-01-15T13: 28: 19 + 00: 00

Those of you who have already managed to go to a new version of 1C: Accounting 8.3 (editors 3.0) managed to notice that it began to work more slowly than twice. Some incomprehensible braces, endless background tasks several times a day, which no one asked for it without our knowledge.

My accountants immediately after the transition, they stated that the new version of 1C: Accounting 3.0 in comparison with the previous ones frankly slows down! And it is simply impossible to work.

I began to understand and very soon found out that the main reason for the fools and the next discontent users are the regulatory and background tasks, many of which are included by default, although there is no need for the absolute majority of accountants.

Well, for example, why should we start the task "Extracting Text" a hundred times a day, if we do not implement full-text (accountants, do not be frightened) Search for all objects of our base.

Or why constantly download exchange rates, if we do not have currency transactions or we do occasionally (and we can click the download courses button).

The same applies to the permanent attempt 1c connect to the site and check and update bank classifiers. What for? I will click on the update Classifiers button, if I do not find the right bank on its bick.

How to do this in the items below.

1. Go to the "Administration" section and in the Action Panel, select "Maintenance" ():

2. In the window that opens, find and select "Regault and Background Tasks":

3. Open each task that has in column "On" It is a daw.

4. Remove the mark from the "Enabled" item and click the "Record and Close" button.

5. Do it with each of the tasks included and enjoy the new edition. In general, in my opinion, it is much better than twice.

At the same time, some of the regulatory tasks disconnected by you will turn on back.

When working in 1C, there are many routine operations that must be launched or to form on schedule performing this or that action, for example: conducting documents or data load in 1C from the site.

I recently posted an article: it's time to automate it:

Regulations and background tasks

The task mechanism is designed to perform any applied or functionality on a schedule or asynchronously.

The task mechanism solves the following tasks:

• The ability to define regulatory procedures at the system configuration phase;
• Execution of specified actions on a schedule;
• Performing a call for a given procedure or asynchronously function, i.e. without waiting for its completion;
• Tracking the progress of a certain task and obtaining its completion status (values \u200b\u200bindicating the success or not successful implementation);
• Receiving a list of current tasks;
• Ability to wait for the completion of one or more tasks;
• Job management (ability to cancel, lock execution, etc.).

The task mechanism consists of the following components:

• Metadata of regulatory tasks;
• Regulatory tasks;
• Background tasks;
• Job scheduler.

Background tasks & are designed to perform applied tasks asynchronously. Background tasks are implemented by the built-in language.

Rules' tasks & are designed to perform applied schedule tasks. Regulatory tasks are stored in the information base and are created on the basis of metadata defined in the configuration. The metadata of the regulatory task contains such information as the name, method, use, etc.

The regulatory task has a schedule that determines which moments of time must be carried out by the method associated with the regulatory task. The schedule is usually set in the information base, but can also be specified at the configuration stage (for example, for predefined regulatory tasks).

The task scheduler is used to plan the execution of regulatory tasks. For each regulatory task, the planner periodically checks whether the current date and time of the schedule of the regulatory task is true. If it matches, the scheduler assigns such a task to execute. To do this, according to this regulatory task, the planner creates a background task that performs real processing.

With the description, I think, enough - I will proceed to implement:

Creating a regulatory task

Method name - The path to the procedure that will be performed in the background task on a specified schedule. The procedure must be in the overall module. It is recommended not to use typical common modules, but create your own. Do not forget that background tasks are executed on the server!

Using - a sign of using a regulatory task.

Predefined- Indicates whether the regulatory task is predefined.

If you want to work as a regulatory task immediately after the room in the database, specify a sign Predefined. Otherwise, you will need to use the Task Console processing or call the task to start programmatically.

Number of repetitions in case of emergency completion - How many times have a restart of the background job, if it was performed with an error.

Repeat interval when an accident failure - What frequentness will be configured to restart the background task if it was performed with an error.

Setting the schedule

schedule Task performance:

Every hour, only one day	PeriodsToistnee \u003d 0, PeriodsTravteraneedyDee \u003d 3600
Every day once a day	PeriodsToistnee \u003d 1, PeriodsTravteraneednya \u003d 0
One day, once	PeriodsTrans: 0.
Every other day once a day	PeriodsOther \u003d 2.
Every hour from 01.00 to 07.00 every day	PeriodsToistnee \u003d 1PeriodHonThe showroom \u003d 3600 pulled \u003d 01.00 Time confer \u003d 07.00
Every Saturday and Sunday at 09.00	PeriodsToistnes \u003d 1DNNnedheli \u003d 6, 7 pulled \u003d 09.00
Every day one week, weekmission week	PeriodsTrans: 1 period \u003d 2
At 01.00 once	Time \u003d 01.00
The last number of each month at 9:00.	PeriodsToistnee \u003d 1 Deniye \u003d -1 pulled \u003d 09.00
Fifth number of each month at 9:00	PeriodsToistnee \u003d 1 Deniye \u003d 5 pulled \u003d 09.00
The second environment of each month at 9:00	PeriodsToistnee \u003d 1Denteliyvyza \u003d 2DNNNYED \u003d 3 Top \u003d 09.00

Features of execution of background tasks file and client-server versions

Mechanisms for performing background tasks in file and client-server variants differ.

In the file version It is necessary to create a selected client process that will make the performance of background tasks. To do this, in the client process, the function of the global configuration context context function should be occupied. Only one client process on the information database should perform the processing of background tasks (and, accordingly, call this function). If the client process is not created for processing background tasks, then when software access, the task manager will be issued to the job mechanism. The client process that performs the processing of background tasks is not recommended for other functions.

After the client process that performs the processing of background tasks is launched, the remaining client processes get the ability to program the mechanism of background tasks, i.e. Can run and manage background tasks.

In the client-server version To perform background tasks, a task scheduler is used, which is physically in the cluster manager. The scheduler for all the background tasks assigned to perform the background tasks receives the least loaded workflow and uses it to perform the appropriate background task. The workflow is tasked and notifies the scheduler about the results of execution.

The client-server version has the ability to block the execution of regulatory tasks. Blocking the execution of regulatory tasks occurs in the following cases:

• The information base has a clear blocking of regulatory tasks. Lock can be installed through the cluster console;
• The information database is set to block the connection. Lock can be installed through the cluster console;
• From the built-in language, the method of setting monopular () with the truth parameter is called;
• In some other cases (for example, when updating the database configuration).

Starting and viewing rules for regulatory tasks You can download here.

Allows us to make any calculations in the system imperceptibly for the user, that is, in the background. Moreover, this mechanism allows us to parallery the calculation process. We can even parallel the procedure that will be performed. To do this, our background task must launch several other background tasks. In this case, the processes are parallelized and, if we have a multiprocessor, multi-core system, our algorithm will work efficiently. After launching several processes, we can say the system that it is necessary to wait for the end of the execution of these processes in order to somehow reduce the result.

For example, in typical configurations, while the user works, a different kind of service background tasks occurs. This may evidence registration log records in which the fact of performing such actions is recorded. And it does not affect the work of the user, he just does not notice them.

Ideally, the background task is implemented in the client-server version, in this case the entire load goes to the server. As for the file option, the work of the background task is possible, but it has some features.

This is what the system is issued if you do not take into account these features, and run the background task in the file version of the information base.

1C background task has some limitations. Because it is running on the server side, then there is no possibility of interactive working with the user. For example, you can not withdraw a message, well, in general, some information. All this data must be maintained within the information base and further process it.

Turning to the assistant syntax, you can get more detailed information about 1C background tasks. Here it should be noted that this object is exclusively software and it is not saved in the database. That is, we create an instance of the class, initialize the properties and run it to execute.

What funds do we have to manage background tasks? This means is the metadata object "Managed Forces". This object has a method "Run"With this method, the background task is started.

It has the following parameters:
"NameMode" - the name of the procedure or function that needs to be performed, and this must be a procedure or a server context function;

"Parameters" - array of parameters, the number of elements of which must correspond to the number of parameters of our procedure / function specified in the parameter "NameMode";

"Key" - A certain key of uniqueness, representing a line from itself, in which the system understands whether to start the background task or such a task has already been launched;

"Name" - Here you can specify an arbitrary description of our method.

Returned value is the object "Background France"containing the current method of the method, the current key and several more properties and methods. One of these methods is the method "Wait for converters". Its task is that we can specify the system so that nothing has been done until the background task will be completed.

Background task 1C 8.2, 8.3 - Example of use

We give an example of working with 1c background tasks. First, create a simple algorithm that will briefly download the 1C system so that we cannot do anything at that time.

For this:

1. Create a common module "ProcessingFounds"which will be compiled on the server side;

2. Let us describe in it export procedure "Production appendix (parameter)"which accepts one string type parameter;

Procedure ProductsPhone [Parameter) Export time \u003d currentData (); While flowing) () - time< = 6 Цикл КонецЦикла ; КонецПроцедуры Процедура КнНажатие() ОбработчикиФоновыхЗаданий. ПроизветиФоновоеВычисление("Some kind of parameter"); Extrudresses

Ready. Now, when you start processing and pressing the button, the system is running for a few seconds, in the process of which nothing can be done. It is just what we needed to do.

Now we will provide a product of these calculations in the background, that is, the background task 1C 8.2, 8.3 was performed, but it did not prevent us.

For this:

1. In the processing, in the Pressing event, the following code is the following code.

Fusion procedure () Parameters \u003d New array; Parameters. Add ( "Some kind of parameter"); Background appearance. Execute "ProcessingFoundsFounds. PlayingFounds", Parameters, new unique identifier, "Test"); Extrudresses

Here, the first parameter we convey the name of the procedure of the general module, and the second is an array of parameters. The third parameter must be transferred to a unique key and a fourth some description of our procedure.

We made in the title article The question is relevant for many system administrators working with this product. As far as possible, we try to talk about the parameters affecting the performance of 1C and discharge popular myths. Today, on the example of one recent case, we want to tell you about another aspect that can seriously affect productivity - regulatory tasks.

Let's start with a real case. Not so long ago, one of our clients turned to us with a complaint about the "brake" 1c from one of his employees. The symptoms were expressed in the fact that after a certain time, the configuration of the TRADE control 10 began to slow down much, and simply hesitated for some time.

With a more detailed analysis of the situation, it turned out that it was only at one employee, and at any workplace, it happened for a long time, but if earlier "brakes" lasted about a second, now, after the update, they can last until 15-20 seconds that Makes the work extremely uncomfortable.

In principle, the source data is already enough to make the first conclusions. We give them again:

• "Brakes" occur constantly, with certain periodicity
• "Slows down" only one user
• "Slows down" at any workplace

To confirm your guesses to look in Settings for accounting parameters:

Indeed, the "problem" user is specified as a user to perform regulatory tasks. As it turned out, once a long time ago, the assignment of Rib autobrame was working on behalf of this user. It remains to see what exactly was the cause of episodic "braking". It is also easy to do:

And here is the "Celebration Celebration" - setting the update of the full-text search index, which was launched once a 2.5 minutes. In this case, the problem was completely solved by turning off the execution of regulatory tasks under this user, but this is not always possible or appropriate, so below we will look at how you can manage the regulatory tasks and how to make sure that they do not have a negative impact on productivity.

Normal app

In configurations based on the usual application of a single toolkit to manage the regulatory tasks there. This is largely due to the fact that at the time of their initial development itself, the concept of regulatory tasks itself was developed rather weakly.

Managing many regulatory tasks is made through the setting of associated subsystems. For example, the settings of the regulatory tasks associated with the exchange of data should be sought in the exchange settings associated with the EGAIS in alcohol trade settings, etc.

At first glance, everything is quite logical, but the absence of a single tool makes it difficult to control the configured regulatory tasks and the optimality of their settings. Well, if the tasks are one - two, and if there are more of them or, as in our case, there is a suspicion of any of the regulatory tasks, but you do not have the idea who has been configured in this database.

In this case, you should use external processing Consolezdans (Jobsconsole.), which is included in the set of standard treatments on the ITS disk. Processing provides a single interface for all tasks and allows them to perform their centralized setting, as well as control the task it runs at the current time.

This list must be carefully learned, all unnecessary tasks should be disabled, and in the necessary lead the schedule in line with urgent needs and common sense. For example, in our case, there is no need to handle the answers of the EGAIS every 30 seconds (this setting is made for testing) and in working mode it will be enough enough to do it once in half an hour.

Controlled application

In configurations based on a managed application, a more significant role is assigned to regulatory assignments, with their help various tasks for servicing the information base and maintain it in the current state, but at the same time it is precisely the regulatory tasks most often become the cause of "brakes".

To manage regulatory tasks, a hotel item is intended in the menu Administration - Support and maintenance.

It can be immediately noted that the tasks were significantly added (for example, we took the same configuration - retail) and their competent setting is capable of significantly improve the performance of the information base. The default settings are made on the basis of the needs of the middle spherical company in vacuum and are not optimal even close.

First of all, turn off what is clearly unnecessary, with which you do not work. Then we optimize the schedule of rarely used functions, let's say the update of the classifier of banks in retail, as well as the control of counterparties, can be carried out once a week in hours or at the end of the working day.

Separate attention should be paid to everything that is associated with the search index. Full-text search is definitely a comfortable thing, but work with its index is a very and very resource-intensive task. Therefore, you should not fall into extreme and abandon it, but you should seriously revise and configure its parameters.

Let's start by S. extract textThis operation allows you to search on the contents of the applied files, so if you do not use them, do not search for them, or you have some images there, then this operation can be disabled, in any case, to perform it in 85 seconds - explicit brute force.

Update index PPD - One of the most resource-intensive operations, defaults once per minute.

And now we think how often in the database is added or information on which you most often search are added? Not clearly every minute, so it will be enough to update the index much less frequently: once an hour, once a day or in general once a week.

Also applies to merging Index PPDIf you update the index once a day, you should configure the merge to execute once a week, while choosing the least interfering time as the start of the task.

These simple operations will allow you without particular damage to the configuration functionality to raise the comfort of working with it to a new level due to the failure of the frequent execution of sufficiently resource-intensive operations. Just do not fall in extremes, competently judge how you need certain opportunities and how often the associated tasks should be performed.

• Tags:

Please Enable JavaScript to View The